Description

This PR addresses a GraphQLError: Cannot query field 'message' on type 'CreateUserTokenError' that occurs when attempting to query the message field directly on the CreateUserTokenError union type.

The root cause is that CreateUserTokenError is a GraphQL union (UnauthenticatedError | ValidationError), and fields cannot be queried directly on union types. All member types of this union, however, implement the ResolverError interface, which exposes the message field.

Code Example

mutation CreateUserToken($input: CreateUserTokenInput!) {
  createUserToken(input: $input) {
    error {
      ... on ResolverError {
        message
      }
    }
    token {
      token
    }
  }
}

Notable Changes

The fix updates the createUserToken mutation query in src/services/access/useGenerateUserToken.ts to use an inline fragment ... on ResolverError { message }. This correctly retrieves the error message when an error occurs, resolving the GraphQL validation error and aligning the frontend query with the backend schema. It also ensures that the existing Zod schema, which expects a message field, is correctly populated.

Screenshots

Link to Sample Entry

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. In 2022 this entity acquired Codecov and as result Sentry is going to need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

Fixes API-E9F